Download to read offline
![Measuring code complexity
public function render() {
$code = null;
if (isset($this->headers['location']) && $this->status['code'] === 200) {
$code = 302;
}
if (!$status = $this->status($code)) {
throw new Exception('Invalid status code');
}
$this->_writeHeader($status);
foreach ($this->headers as $name => $value) {
$key = strtolower($name);
if ($key == 'location') {
$this->_writeHeader("Location: {$value}", $this->status['code']);
} elseif ($key == 'download') {
$this->_writeHeader('Content-Disposition: attachment; filename="' . $val
} elseif (is_array($value)) {
$this->_writeHeader(
array_map(function($v) use ($name) { return "{$name}: {$v}"; }, $val
);
} elseif (!is_numeric($name)) {
$this->_writeHeader("{$name}: {$value}");
}
}
}](https://image.slidesharecdn.com/measuringyourcode2-0-100610113554-phpapp02/75/Measuring-Your-Code-32-2048.jpg)
Uploaded byNate Abele
Measuring Your Code
The talk discusses the importance of measuring software development through metrics like code complexity, coverage, and documentation to drive continuous improvement. Key concepts include using lower-level metrics for measurement instead of high-level project metrics, the role of continuous integration, and techniques for standardizing code. The document emphasizes the necessity of metrics in management and quality assurance within software projects.
![Support, Monitoring, Continuous Improvement & Scaling Agentic Automation [3/3]](https://cdn.slidesharecdn.com/ss_thumbnails/agenticcommunityseries-day3-cfd-251120170304-ddef8112-thumbnail.jpg?width=640&height=640&fit=bounds)
Measuring Your Code
- 1. Measuring your code A talk by Nate Abele @nateabele nate.abele@gmail.com
- 2. Feedback http://joind.in/1601
- 3.
- 5. Coercion, red bars& broken windows
- 6.
- 7.
- 8. Or at theleast, continuous improvement
- 9. a.k.a. (kaizen)
- 10. What people usuallythink Estimating costs Projecting deadlines Managerial BS!
- 11. Client Spec Sheetsome paraphrased) (actual bullet points, Flash intro with no load time User account logins, password optional Ajax chat “Like Google”
- 12. ...and my personalfavorite Social network
- 13. Measurement is anessential element of management; there is little chance of controlling what we can not measure. - Wikipedia, “Software metric”
- 14.
- 15.
- 17. Cognitive Dissonance * Engineers deal with tangible, immutable constraints, like gravity The practice of developing software is an inherently creative discipline * Thank you, Jones
- 18. Cognitive Dissonance Developer constraints (scope, schedule, budget) potentially / often in flux Software is inter-related; working on one part changes the others No project is exactly the same as another
- 19. Conclusion It’s not useful to measure high-level, intangible things like whole projects This is where scrum comes in handy Instead, we can use lower-level, more concrete measurements
- 20. What can wemeasure?
- 21.
- 22. More specifically... Unit test coverage Complexity Speed Documentation
- 23. More specifically... Standards conformance Refactoration!
- 24. Backing up... What is a metric? Measurement assigns numbers based on well- defined meaning - Sometimes the environment must be modified - Special development procedures that track various activities - Wikipedia (paraphrased) You can cheat and use booleans, too
- 25. Notes on continuousintegration A build system Runs on every code commit Runs tests Reports
- 26.
- 27. PHP Code Sniffer PEAR Package: http://pear.php.net/package/PHP_CodeSniffer Checks conformance of a set of files against a series of classes called “sniffs”
- 28.
- 29.
- 30. This is importantbecause things are standardized
- 31. Measuring code complexity Cyclomatic complexity Directly measures the number of linearly independent paths through a program's source code. a.k.a. 1 + the number of times it branches
- 32. Measuring code complexity public function render() { $code = null; if (isset($this->headers['location']) && $this->status['code'] === 200) { $code = 302; } if (!$status = $this->status($code)) { throw new Exception('Invalid status code'); } $this->_writeHeader($status); foreach ($this->headers as $name => $value) { $key = strtolower($name); if ($key == 'location') { $this->_writeHeader("Location: {$value}", $this->status['code']); } elseif ($key == 'download') { $this->_writeHeader('Content-Disposition: attachment; filename="' . $val } elseif (is_array($value)) { $this->_writeHeader( array_map(function($v) use ($name) { return "{$name}: {$v}"; }, $val ); } elseif (!is_numeric($name)) { $this->_writeHeader("{$name}: {$value}"); } } }
- 33.
- 34. Measuring documentation coverage Check it out @ http://thechaw.com/api_generator
- 35. Measuring documentation coverage Check it out: http://thechaw.com/api_generator A series of rules Assigns weights based on docblock content and various docblock tags
- 36. Measuring documentation coverage Basic checks: Do doc tags exist? Incomplete @param tags? Do @param tags match actual params? Does it have a @link to the man page?
- 37.
- 38. Profiling Get timing / memory usage on every test run Granular, get statistics per test method Using continuous integration, code is profiled on each commit, all on a granular level
- 39.
- 40. CakePHP 1.2 releasecycle 1.2 alpha 1.2 beta 1.2 RC1 1.2 RC2 1.2 RC3 1.2 RC4
- 41. Metrics are yourcanary in the coal mine of your development cycle
- 42. By tracking profilerstats (and other metrics), we can see trends over time, and catch problems before they become problems
- 43. Plus, who doesn’tlike pretty graphs?
- 44. Finding things tomeasure Lithium Inspector class Lithium Parser class Based on the awesome work of Sean Coates http://github.com/scoates/tokalizer
- 45. Finding things tomeasure
- 46. Finding things tomeasure
- 47. Finding things tomeasure
- 48. Finding things tomeasure
- 49. Finding things tomeasure
- 50. In a dynamiclanguage like PHP, this is a hard problem.
- 51. However, deep codeintrospection allows us to ask & answer some very interesting questions
- 52. Project mess detectionin PHPUnit
- 53. Beyond copy-paste detection& into pattern recognition
- 54.
- 55. Can “good code”be quantified??
- 56. When is “goodenough”... good enough?
- 57.
- 58. Incentives and socialcoercion
- 59. Choose your ownadventure!
- 60. Go write bettercode